[7.x] [APM] Sets up APM with new shared Kibana core context (#43920) #44139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
|
retest |
2 similar comments
|
retest |
|
retest |
💔 Build Failed |
|
retest |
💔 Build Failed |
jasonrhodes
force-pushed
the
backport/7.x/pr-43920
branch
from
151b868
to
08dc7fe
Compare
💔 Build Failed |
|
@elasticmachine, run elasticsearch-ci/docs |
💚 Build Succeeded |
💚 Build Succeeded |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Manual backport of #43920
Note: After fixing a conflict in the backport folder, I attempted to do
git cherry-pick --continuebut it failed because it couldn't find the precommit hook script? Eventually I had to just commit the resolved files with a message I believed to be close to what the auto-generated one would've been, then push the branch and create the PR myself manually here.